plugins/withWebRTCFrameworkFix.js (1)

24-27: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Marker check can skip the new all-target fix on already-patched Podfiles.

If the Podfile already contains this marker from a previous single-target patch, the plugin returns early and never applies the new all-target loop, so the upgrade path can remain broken.

Suggested fix

-      const marker = 'CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES';
-      if (contents.includes(marker)) {
+      const marker = "installer.pods_project.targets.each do |target|";
+      if (contents.includes(marker)) {
         return config;
       }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@plugins/withWebRTCFrameworkFix.js` around lines 24 - 27, The current
early-return checks only for the marker
'CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES' in contents and returns
config, which skips adding the new all-target loop when a Podfile was previously
patched for a single target; update the logic in withWebRTCFrameworkFix.js so
that instead of returning immediately when contents.includes(marker) is true you
also verify the presence of the new all-target loop (e.g., the loop text you
intend to inject) and only return if both the marker and the all-target loop
exist; if the marker exists but the all-target loop is missing, continue to
apply the new patch to inject the all-target loop before returning config.